Multicore shared cache operation engine

ABSTRACT

Techniques including receiving configuration information for a trigger control channel of the one or more trigger control channels, the configuration information defining a first one or more triggering events, receiving a first memory management command, store the first memory management command, detecting a first one or more triggering events, and triggering the stored first memory management command based on the detected first one or more triggering events.

CROSS-REFERENCE TO RELATED APPLICATIONS

This application claims priority to U.S. Provisional Application No. 62/745,842 filed Oct. 15, 2018, which is hereby incorporated by reference.

BACKGROUND

In a multi-core coherent system, multiple processor and system components share the same memory resources, such as on-chip and off-chip memories. Memory caches (e.g., caches) typically are an amount of high-speed memory located operationally near (e.g., close to) a processor. A cache is more operationally nearer to a processor based on latency of the cache, that is, how many processor clock cycles for the cache to fulfill a memory request. Generally, cache memory closest to a processor includes a level 1 (L1) cache that is often directly on a die with the processor. Many processors also include a larger level 2 (L2) cache. This L2 cache is generally slower than the L1 cache but may still be on the die with the processor cores. The L2 cache may be a per processor core cache or shared across multiple cores. Often, a larger, slower L3 cache, either on die, as a separate component, or another portion of a system on a chip (SoC) is also available to the processor cores.

Ideally, if all components had the same cache structure, and would access shared resources through cache transactions, all the accesses would be identical throughout the entire system, aligned with the cache block boundaries. But usually, some components have no caches, or, different components have different cache block sizes. For a heterogeneous system, accesses to the shared resources can have different attributes, types and sizes. For example, a central processing unit (CPU) of a system may have different sized or different speed memory caches as compared to a digital signal processor (DSP) of the system. On the other hand, the shared resources may also be in different formats with respect to memory bank structures, access sizes, access latencies and physical locations on the chip.

To maintain data coherency, a coherence interconnect is usually added in between the master components and shared resources to arbitrate among multiple masters' requests and guarantee data consistency when data blocks are modified for each resource slave. With various accesses from different components to different slaves, the interconnect usually handles the accesses in a serial fashion to guarantee atomicity and to meet slaves access requests. This makes the interconnect the access bottleneck for a multi-core mufti-slave coherence system.

To reduce CPU cache miss stall overhead, cache components could issue cache allocate accesses with the request that the lower level memory hierarchy must return the “critical line first” to un-stall the CPU, then the non-critical line to finish the line fill. In a shared memory system, to serve one CPU's “critical line first” request could potentially extend the other CPU's stall overhead and reduce the shared memory throughput if the memory access types and sizes are not considered. The problem therefore to solve is how to serve memory accesses from multiple system components to provide low overall CPU stall overhead and guarantee maximum memory throughput.

Due to the increased number of shared components and expended shareable memory space, to support data consistency while reducing memory access latency for all cores while maintaining maximum shared memory bandwidth and throughput is a challenge.

SUMMARY

This disclosure relates to a processing system comprising one or more processors, a cache memory coupled to the one or more processors, and a memory controller comprising one or more trigger control channels configured to receive configuration information for a trigger control channel of the one or more trigger control channels, the configuration information defining the first one or more triggering events, receive a first memory management command, store the first memory management command, detect a first one or more triggering events, and trigger the stored first memory management command based on the detected first one or more triggering events.

Another aspect of the present disclosure relates to a processing device comprising one or more processors, a cache memory coupled to the one or more processors, and a memory controller comprising circuitry for one or more trigger control channels, the circuitry for the one or more trigger control channels configured to receive configuration information for a trigger control channel of the one or more trigger control channels, the configuration information defining a first one or more triggering events, receive a first memory management command, store the first memory management command, detect a first one or more triggering events, and trigger the stored first memory management command based on the detected first one or more triggering events.

Another aspect of the present disclosure relates to a method including receiving configuration information for a trigger control channel of the one or more trigger control channels, the configuration information defining a first one or more triggering events, receiving a first memory management command, store the first memory management command, detecting a first one or more triggering events, and triggering the stored first memory management command based on the detected first one or more triggering events.

BRIEF DESCRIPTION OF THE DRAWINGS

For a detailed description of various examples, reference will now be made to the accompanying drawings in which:

FIG. 1 illustrates a multi-core processing system, in accordance with aspects of the present disclosure.

FIG. 2 is a functional block diagram of a MSMC, in accordance with aspects of the present disclosure.

FIG. 3 is a block diagram of a DRU, in accordance with aspects of the present disclosure.

FIG. 4 is a flow diagram illustrating a technique for accessing memory by a memory controller, in accordance with aspects of the present disclosure.

DETAILED DESCRIPTION

Specific embodiments of the invention will now be described in detail with reference to the accompanying figures. In the following detailed description of embodiments of the invention, numerous specific details are set forth in order to provide a more thorough understanding of the invention. However, it will be apparent to one of ordinary skill in the art that the invention may be practiced without these specific details. In other instances, well-known features have not been described in detail to avoid unnecessarily complicating the description.

High performance computing has taken on even greater importance with the advent of the Internet and cloud computing. To ensure the responsiveness of networks, online processing nodes and storage systems must have extremely robust processing capabilities and exceedingly fast data-throughput rates. Robotics, medical imaging systems, visual inspection systems, electronic test equipment, and high-performance wireless and communication systems, for example, must be able to process an extremely large volume of data with a high degree of precision. A multi-core architecture that embodies an aspect of the present invention will be described herein. In a typically embodiment, a multi-core system is implemented as a single system on chip (SoC).

FIG. 1 is a functional block diagram of a multi-core processing system 100, in accordance with aspects of the present disclosure. System 100 is a multi-core SoC that includes a processing cluster 102 including one or more processor packages 104. The one or more processor packages 104 may include one or more types of processors, such as a CPU, GPU, DSP, etc. As an example, a processing cluster 102 may include a set of processor packages split between DSP, CPU, and GPU processor packages. Each processor package 104 may include one or more processing cores. As used herein, the term “core” refers to a processing module that may contain an instruction processor, such as a digital signal processor (DSP) or other type of microprocessor. Each processor package also contains one or more caches 108. These caches 108 may include one or more L1 caches, and one or more L2 caches. For example, a processor package 104 may include four cores, each core including an L1 data cache and L1 instruction cache, along with an L2 cache shared by the four cores.

The multi-core processing system 100 also includes a multi-core shared memory controller (MSMC) 110, through which is connected one or more external memories 114 and input/output direct memory access clients 116. The MSMC 110 also includes an on-chip internal memory 112 system which is directly managed by the MSMC 110. In certain embodiments, the MSMC 110 helps manage traffic between multiple processor cores, other mastering peripherals or direct memory access (DMA) and allows processor packages 104 to dynamically share the internal and external memories for both program instructions and data. The MSMC internal memory 112 offers flexibility to programmers by allowing portions to be configured as shared level-2 RAM (SL2) or shared level-3 RAM (SL3). External memory 114 may be connected through the MSMC 110 along with the internal shared memory 112 via a memory interface (not shown), rather than to chip system interconnect as has traditionally been done on embedded processor architectures, providing a fast path for software execution. In this embodiment, external memory may be treated as SL3 memory and therefore cacheable in L1 and L2 (e.g., caches 108).

FIG. 2 is a functional block diagram of a MSMC 200, in accordance with aspects of the present disclosure. The MSMC 200 includes a MSMC core logic 202 defining the primary logic circuits of the MSMC. The MSMC 200 is configured to provide an interconnect between master peripherals (e.g., devices that access memory, such as processors, processor packages, direct memory access/input output devices, etc.) and slave peripherals (e.g., memory devices, such as double data rate random access memory, other types of random access memory, direct memory access/input output devices, etc.). The master peripherals may or may not include caches. The MSMC 200 is configured to provide hardware based memory coherency between master peripherals connected to the MSMC 200 even in cases in which the master peripherals include their own caches. The MSMC 200 may further provide a coherent level 3 cache accessible to the master peripherals and/or additional memory space (e.g., scratch pad memory) accessible to the master peripherals.

The MSMC core 202 includes a plurality of coherent slave interfaces 206A-D. While in the illustrated example, the MSMC core 202 includes thirteen coherent slave interfaces 202 (only four are shown for conciseness), other implementations of the MSMC core 202 may include a different number of coherent slave interfaces 206. Each of the coherent slave interfaces 206A-D is configured to connect to one or more corresponding master peripherals. Example master peripherals include a processor, a processor package, a direct memory access device, an input/output device, etc. Each of the coherent slave interfaces 206 is configured to transmit data and instructions between the corresponding master peripheral and the MSMC core 202. For example, the first coherent slave interface 206A may receive a read request from a master peripheral connected to the first coherent slave interface 206A and relay the read request to other components of the MSMC core 202. Further, the first coherent slave interface 206A may transmit a response to the read request from the MSMC core 202 to the master peripheral. In some implementations, the coherent slave interfaces 206 correspond to 512 bit or 256 bit interfaces and support 48 bit physical addressing of memory locations.

In the illustrated example, a thirteenth coherent slave interface 206D is connected to a common bus architecture (CBA) system on chip (SOC) switch 208. The CBA SOC switch 208 may be connected to a plurality of master peripherals and be configured to provide a switched connection between the plurality of master peripherals and the MSMC core 202. While not illustrated, additional ones of the coherent slave interfaces 206 may be connected to a corresponding CBA. Alternatively, in some implementations, none of the coherent slave interfaces 206 is connected to a CBA SOC switch.

In some implementations, one or more of the coherent slave interfaces 206 interfaces with the corresponding master peripheral through a MSMC bridge 210 configured to provide one or more translation services between the master peripheral connected to the MSMC bridge 210 and the MSMC core 202. For example, ARM v7 and v8 devices utilizing the AXI/ACE and/or the Skyros protocols may be connected to the MSMC 200, while the MSMC core 202 may be configured to operate according to a coherence streaming credit-based protocol, such as Multi-core bus architecture (MBA). The MSMC bridge 210 helps convert between the various protocols, to provide bus width conversion, clock conversion, voltage conversion, or a combination thereof. In addition or in the alternative to such translation services, the MSMC bridge 210 may cache prewarming support via an Accelerator Coherency Port (ACP) interface for accessing a cache memory of a coupled master peripheral and data error correcting code (ECC) detection and generation. In the illustrated example, the first coherent slave interface 206A is connected to a first MSMC bridge 210A and an eleventh coherent slave interface 210B is connected to a second MSMC bridge 210B. In other examples, more or fewer (e.g., 0) of the coherent slave interfaces 206 are connected to a corresponding MSMC bridge.

The MSMC core logic 202 includes an arbitration and data path manager 204. The arbitration and data path manager 204 includes a data path (e.g., a collection of wires, traces, other conductive elements, etc.) between the coherent slave interfaces 206 and other components of the MSMC core logic 202. The arbitration and data path manager 204 further includes logic configured to establish virtual channels between components of the MSMC 200 over shared physical connections (e.g., the data path). In addition, the arbitration and data path manager 204 is configured to arbitrate access to these virtual channels over the shared physical connections. Using virtual channels over shared physical connections within the MSMC 200 may reduce a number of connections and an amount of wiring used within the MSMC 200 as compared to implementations that rely on a crossbar switch for connectivity between components. In some implementations, the arbitration and data path 204 includes hardware logic configured to perform the arbitration operations described herein. In alternative examples, the arbitration and data path 204 includes a processing device configured to execute instructions (e.g., stored in a memory of the arbitration and data path 204) to perform the arbitration operations described herein. As described further herein, additional components of the MSMC 200 may include arbitration logic (e.g., hardware configured to perform arbitration operations, a processor configure to execute arbitration instructions, or a combination thereof). The arbitration and data path 204 may select an arbitration winner to place on the shared physical connections from among a plurality of requests (e.g., read requests, write requests, snoop requests, etc.) based on a priority level associated with a requestor, based on a fair-share or round robin fairness level, based on a starvation indicator, or a combination thereof.

The arbitration and data path 204 further includes a coherency controller 224. The coherency controller 224 includes a snoop filter 212. The snoop filter 212 is a hardware unit that store information indicating which (if any) of the master peripherals stores data associated with lines of memory of memory devices connected to the MSMC 200. The coherency controller 224 is configured to maintain coherency of shared memory based on contents of the snoop filter 212.

The MSMC 200 further includes a MSMC configuration component 214 connected to the arbitration and data path 204. The MSMC configuration component 214 stores various configuration settings associated with the MSMC 200. In some implementations, the MSMC configuration component 214 includes additional arbitration logic (e.g., hardware arbitration logic, a processor configured to execute software arbitration logic, or a combination thereof).

The MSMC 200 further includes a plurality of cache tag banks 216. In the illustrated example, the MSMC 200 includes four cache tag banks 216A-D. In other implementations, the MSMC 200 includes a different number of cache tag banks 216 (e.g., 1 or more). The cache tag banks 216 are connected to the arbitration and data path 204. Each of the cache tag banks 216 is configured to store “tags” indicating memory locations in memory devices connected to the MSMC 200. Each entry in the snoop filter 212 corresponds to a corresponding one of the tags in the cache tag banks 216. Thus, each entry in the snoop filter indicates whether data associated with a particular memory location is stored in one of the master peripherals.

Each of the cache tag banks 216 is connected to a corresponding RAM bank 218. For example, a first cache tag bank 216A is connected to a first RAM bank 218A etc. Each entry in the RAM banks 218 is associated with a corresponding entry in the cache tag banks 216 and a corresponding entry in the snoop filter 212. Entries in the RAM banks 218 may be used as an additional cache or as additional memory space based on a setting stored in the MSMC configuration component 214. The cache tag banks 216 and the RAM banks 218 may correspond to RAM modules (e.g., static RAM). While not illustrated in FIG. 2, the MSMC 200 may include read modify write queues connected to each of the RAM banks 218. These read modify write queues may include arbitration logic, buffers, or a combination thereof.

The MSMC 200 further includes an external memory interleave component 220 connected to the cache tag banks 216 and the RAM banks 218. One or more external memory master interfaces 222 are connected to the external memory interleave 220. The external memory interfaces 222 are configured to connect to external memory devices (e.g., DDR devices, direct memory access input/output (DMA/IO) devices, etc.) and to exchange messages between the external memory devices and the MSMC 200. The external memory devices may include, for example, the external memories 114 of FIG. 1, the DMA/IO clients 116, of FIG. 1, or a combination thereof. The external memory interleave component 220 is configured to interleave or separate address spaces assigned to the external memory master interfaces 222. While two external memory master interfaces 222A-B are shown, other implementations of the MSMC 200 may include a different number of external memory master interfaces 222.

The MSMC core 202 also includes a data routing unit (DRU) 250, which helps provide integrated address translation and cache prewarming functionality and is coupled to a packet streaming interface link (PSI-L) interface 252, which is a shared messaging interface to a system wide bus supporting DMA control messaging. The DRU includes an integrated DRU memory management unit (MMU) 254.

DMA control messaging may be used by applications to perform memory operations, such as copy or fill operations, in an attempt to reduce the latency time needed to access that memory. Additionally, DMA control messaging may be used to offload memory management tasks from a processor. However, traditional DMA controls have been limited to using physical addresses rather than virtual memory addresses. Virtualized memory allows applications to access memory using a set of virtual memory addresses without having to have any knowledge of the physical memory addresses. An abstraction layer handles translating between the virtual memory addresses and physical addresses. Typically, this abstraction layer is accessed by application software via a supervisor privileged space. For example, an application having a virtual address for a memory location and seeking to send a DMA control message may first make a request into a privileged process, such as an operating system kernel requesting a translation between the virtual address to a physical address prior to sending the DMA control message. In cases where the memory operation crosses memory pages, the application may have to make separate translation requests for each memory page. Additionally, when a task first starts, memory caches for a processor may be “cold” as no data has yet been accessed from memory and these caches have not yet been filled. The costs for the initial memory fill and abstraction layer translations can bottleneck certain tasks, such as small to medium sized tasks which access large amounts of memory. Improvements to DMA control message operations may help improve these bottlenecks.

FIG. 3 is a block diagram of a DRU 300, in accordance with aspects of the present disclosure. In some implementations, the DRU 300 corresponds to the DRU 250 of FIG. 2. The DRU 300 can operate on two general memory access commands, a transfer request (TR) command to move data from a source location to a destination location, and a cache request (CR) command to send messages to a specified cache controller or MMUs to prepare the cache for future operations by loading data into memory caches which are operationally closer to the processor cores, such as a L1 or L2 cache, as compared to main memory or another cache that may be organizationally separated from the processor cores. The DRU 300 may receive these commands via one or more interfaces. In this example, two interfaces are provided, a direct write of a memory mapped register (MMR) 302 and via a PSI-L message 304 via a PSI-L interface 344 to a PSI-L bus. In certain cases, the memory access command and the interface used to provide the memory access command may indicate the memory access command type, which may be used to determine how a response to the memory access command is provided.

The PSI-L bus may be a system bus that provides for DMA access and events across the multi-core processing system, as well as for connected peripherals outside of the multi-core processing system, such as power management controllers, security controllers, etc. The PSI-L interface 344 connects the DRU 300 with the PSI-L bus of the processing system. In certain cases, the PSI-L may carry messages and events. PSI-L messages may be directed from one component of the processing system to another, for example from an entity, such as an application, peripheral, processor, etc., to the DRU. In certain cases, sent PSI-L messages receive a response. PSI-L events may be placed on and distributed by the PSI-L bus by one or more components of the processing system. One or more other components on the PSI-L bus may be configured to receive the event and act on the event. In certain cases, PSI-L events do not require a response.

The PSI-L message 304 may include a TR command. The PSI-L message 304 may be received by the DRU 300 and checked for validity. If the TR command fails a validity check, a channel ownership check, or transfer buffer 306 fullness check, a TR error response may be sent back by placing a return status message 308, including the error message, in the response buffer 310. If the TR command is accepted, then an acknowledgement may be sent in the return status message. In certain cases, the response buffer 310 may be a first in, first out (FIFO) buffer. The return status message 308 may be formatted as a PSI-L message by the data formatter 312 and the resulting PSI-L message 342 sent, via the PSI-L interface 344, to a requesting entity which sent the TR command.

A relatively low-overhead way of submitting a TR command, as compared to submitting a TR command via a PSI-L message, may also be provided using the MMR 302. According to certain aspects, a core of the multi-core system may submit a TR request by writing the TR request to the MMR circuit 302. The MMR may be a register of the DRU 300. In certain cases, the MSMC may include a set of registers and/or memory ranges which may be associated with the DRU 300, such as one or more registers in the MSMC configuration component 214. When an entity writes data to this associated memory range, the data is copied to the MMR 302 and passed into the transfer buffer 306. The transfer buffer 306 may be a FIFO buffer into which TR commands may be queued for execution. In certain cases, the TR request may apply to any memory accessible to the DRU 300, allowing the core to perform cache maintenance operations across the multi-core system, including for other cores.

The MMR 302, in certain embodiments, may include two sets of registers, an atomic submission register and a non-atomic submission register. The atomic submission register accepts a single 64 byte TR command, checks the values of the burst are valid values, pushes the TR command into the transfer buffer 306 for processing, and writes a return status message 308 for the TR command to the response buffer 310 for output as a PSI-L event. In certain cases, the MMR 302 may be used to submit TR commands but may not support messaging the results of the TR command, and an indication of the result of the TR command submitted by the MMR 302 may be output as a PSI-L event, as discussed above.

The non-atomic submission register provides a set of register fields (e.g., bits or designated set of bits) which may be written into over multiple cycles rather than in a single burst. When one or more fields of the register, such as a type field, is set, the contents of the non-atomic submission register may be checked and pushed into the transfer buffer 306 for processing and an indication of the result of the TR command submitted by the MMR 302 may be output as a PSI-L event, as discussed above.

Commands for the DRU may also be issued based on one or more events received at one or more trigger control channels 316A-316X. In certain cases, multiple trigger control channels 316A-316X may be used in parallel on common hardware and the trigger control channels 316A-316X may be independently triggered by received local events 318A-318X and/or PSI-L global events 320A-320X. In certain cases, local events 318A-318X may be events sent from within a local subsystem controlled by the DRU and local events may be triggered by setting one or more bits in a local events bus 346. PSI-L global events 320A-320X may be triggered via a PSI-L event received via the PSI-L interface 344. When a trigger control channel is triggered, local events 348A-348X may be output to the local events bus 346.

Each trigger control channel may be configured, prior to use, to be responsive to (e.g., triggered by) a particular event, either a particular local event or a particular PSI-L global event. In certain cases, the trigger control channels 316A-316X may be controlled in multiple parts, for example, via a non-realtime configuration, intended to be controlled by a single master, and a realtime configuration controlled by a software process that owns the trigger control channel. Control of the trigger control channels 316A-316X may be set up via one or more received channel configuration commands.

Non-realtime configuration may be performed, for example, by a single master, such as a privileged process, such as a kernel application. The single master may receive a request to configure a trigger control channel from an entity. The single master then initiates a non-realtime configuration via MMR writes to a particular region of channel configuration registers 322, where regions of the channel configuration registers 322 correlate to a particular trigger control channel being configured. The configuration includes fields which allow the particular trigger control channel to be assigned, an interface to use to obtain the TR command, such as via the MMR 302 or PSI-L message 304, which queue of one or more queues 330 a triggered TR command should be sent to, and one or more events to output on the PSI-L bus after the TR command is triggered. The trigger control channel being configured then obtains the TR command from the assigned interface and stores the TR command. In certain cases, the TR command includes triggering information. The triggering information indicates to the trigger control channel what events the trigger control is responsive to (e.g. triggering events). These events may be particular local events internal to the memory controller or global events received via the PSI-L interface 344. Once the non-realtime configuration is performed for the particular channel, a realtime configuration register of the channel configuration registers 322 may be written by the single master to enable the trigger control channel. In certain cases, a trigger control channel can be configured with one or more triggers. The triggers can be a local event, or a PSI-L global event. Realtime configuration may also be used to pause or teardown the trigger control channel.

Once a trigger control channel is activated, the channel waits until the appropriate trigger is received. For example, a peripheral may configure a particular trigger control channel, in this example trigger control channel 316B, to respond to PSI-L events and, after activation of the trigger control channel 316B, the peripheral may send a triggering PSI-L event 320B to the trigger control channel 316B. Once triggered, the TR command is sent by the trigger control channels 316A-316X. The sent TR commands are arbitrated by the channel arbitrator 324 for translation by the subtiler 326 into an op code operation addressed to the appropriate memory. In certain cases, the arbitration is based on a fixed priority associated with the channel and a round robin queue arbitration may be used for queue arbitration to determine the winning active trigger control channel. In certain cases, a particular trigger control channel, such as trigger control channel 316B, may be configured to send a request for a single op code operation and the trigger control channel cannot send another request until the previous request has been processed by the subtiler 326.

In accordance with aspects of the present disclosure, the subtiler 326 includes a memory management unit (MMU) 328. In some implementations, the MMU 328 corresponds to the MMU 254 of FIG. 2. The MMU 328 helps translate virtual memory addresses to physical memory addresses for the various memories that the DRU can address, for example, using a set of page tables to map virtual page numbers to physical page numbers. In certain cases, the MMU 328 may include multiple fully associative micro translation lookaside buffers (uTLBs) which are accessible and software manageable, along with one or more associative translation lookaside buffers (TLBs) caches for caching system page translations. In use, an entity, such as an application, peripheral, processor, etc., may be permitted to access a particular virtual address range for caching data associated with the application. The entity may then issue DMA requests, for example via TR commands, to perform actions on virtual memory addresses within the virtual address range without having to first translate the virtual memory addresses to physical memory addresses. As the entity can issue DMA requests using virtual memory addresses, the entity may be able to avoid calling a supervisor process or other abstraction layer to first translate the virtual memory addresses. Rather, virtual memory addresses in a TR command, received from the entity, are translated by the MMU to physical memory addresses. The MMU 328 may be able to translate virtual memory addresses to physical memory addresses for each memory the DRU can access, including, for example, internal and external memory of the MSMC, along with L2 caches for the processor packages.

In certain cases, the DRU can have multiple queues and perform one read or one write to a memory at a time. Arbitration of the queues may be used to determine an order in which the TR commands may be issued. The subtiler 326 takes the winning trigger control channel and generates one or more op code operations using the translated physical memory addresses, by, for example, breaking up a larger TR into a set of smaller transactions. The subtiler 326 pushes the op code operations into one or more queues 330 based, for example, on an indication in the TR command on which queue the TR command should be placed. In certain cases, the one or more queues 330 may include multiple types of queues which operate independently of each other. In this example, the one or more queues 330 include one or more priority queues 332A-332B and one or more round robin queues 334A-334C. The DRU may be configured to give priority to the one or more priority queues 332A-332B. For example, the priority queues may be configured such that priority queue 332A has a higher priority than priority queue 332B, which would in turn have a higher priority than another priority queue (not shown). The one or more priority queues 332A-332B (and any other priority queues) may all have priority over the one or more round robin queues 334A-334C. In certain cases, the TR command may specify a fixed priority value for the command associated with a particular priority queue and the subtiler 326 may place those TR commands (and associated op code operations) into the respective priority queue. Each queue may also be configured so that a number of consecutive commands that may be placed into the queue. As an example, priority queue 332A may be configured to accept four consecutive commands. If the subtiler 326 has five op code operations with fixed priority values associated with priority queue 332A, the subtiler 326 may place four of the op code operations into the priority queue 332A. The subtiler 326 may then stop issuing commands until at least one of the other TR commands is cleared from priority queue 332A. Then the subtiler 326 may place the fifth op code operation into priority queue 332A. A priority arbitrator 336 performs arbitration as to the priority queues 332A-332B based on the priority associated with the individual priority queues.

As the one or more priority queues 332A-332B have priority over the round robin queues 334A-334C, once the one or more priority queues 332A-332B are empty, the round robin queues 334A-334C are arbitrated in a round robin fashion, for example, such that each round robin queue may send a specified number of transactions through before the next round robin queue is selected to send the specified number of transactions. Thus, each time arbitration is performed by the round robin arbitrator 338 for the one or more round robin queues 334A-334C, the round robin queue below the current round robin queue will be the highest priority and the current round robin queue will be the lowest priority. If an op code operation gets placed into a priority queue, the priority queue is selected, and the current round robin queue retains the highest priority of the round robin queues. Once an op code operation is selected from the one or more queues 330, the op code operation is output via an output bus 340 to the MSMC central arbitrator (e.g., arbitration and data path 204 of FIG. 2) for output to the respective memory.

In cases where the TR command is a read TR command (e.g., a TR which reads data from the memory), once the requested read is performed by the memory, the requested block of data is received in a return status message 308, which is pushed onto the response buffer 310 The response is then formatted by the data formatter 312 for output. The data formatter 312 may interface with multiple busses for outputting, based on the information to be output. For example, if the TR includes multiple loops to load data and specifies a particular loop in which to send an event associated with the TR after the second loop, the data formatter 312 may count the returns from the loops and output the event after the second loop result is received.

In certain cases, write TR commands may be performed after a previous read command has been completed and a response received. If a write TR command is preceded by a read TR command, arbitration may skip the write TR command or stop if a response to the read TR command has not been received. A write TR may be broken up into multiple write op code operations and these multiple write op code operations may be output to the MSMC central arbitrator (e.g., arbitration and data path 204 of FIG. 2) for transmission to the appropriate memory prior to generating a write completion message. Once all the responses to the multiple write op code operations are received, the write completion message may be output.

In addition to TR commands, the DRU may also support CR commands. In certain cases, CR commands may be a type of TR command and may be used to place data into an appropriate memory or cache closer to a core than main memory prior to the data being needed. By preloading the data, when the data is needed by the core, the core is able to find the data in the memory or cache quickly without having to request the data from, for example, main memory or persistent storage. As an example, if an entity knows that a core will soon need data that is not currently cached (e.g., data not used previously, just acquired data, etc.), the entity may issue a CR command to prewarm a cache associated with the core. This CR command may be targeted to the same core or another core. For example, the CR command may write data into a L2 cache of a processor package that is shared among the cores of the processor package.

In accordance with aspects of the present disclosure, how a CR command is passed to the target memory varies based on the memory or cache being targeted. As an example, a received CR command may target an L2 cache of a processor package. The subtiler 326 may translate the CR command to a read op code operation. The read op code operation may include an indication that the read op code operation is a prewarming operation and is passed, via the output bus 340, to the MSMC. Based on the indication that the read op code is a prewarming operation, the MSMC routes the read op code operation to the memory controller of the appropriate memory. By issuing a read op code to the memory controller, the memory controller may attempt to load the requested data into the L2 cache to fulfill the read. Once the requested data is stored in the L2 cache, the memory controller may send a return message indicating that the load was successful to the MSMC. This message may be received by the response buffer 310 and may be output at PSI-L output 342 as a PSI-L event. As another example, the subtiler 326, in conjunction with the MMU 328, may attempt to prewarm an L3 cache. The subtiler 326 may format the CR command to the L3 cache as a cache read op code and pass the cache read, via the output bus 340 and the MSMC, to the L3 cache memory itself. The L3 cache then loads the appropriate data into the L3 cache and may return a response indicating the load was successful, and this response may also include the data pulled into the L3 cache. This return message may, in certain cases, be discarded.

FIG. 4 is a flow diagram illustrating a technique 400 for accessing memory by a memory controller, in accordance with aspects of the present disclosure. At block 402, a trigger control channel receives configuration information, the configuration information defining a first one or more triggering events. As an example, the memory controller may receive, from an entity, including a peripheral that is outside of the processing system such as a chip separate from an SoC, configuration information. The configuration information may be received via a privileged process and the configuration information may include information defining trigger events for the channel, along with an indication of an interface that may be used to obtain a memory management command.

At block 404, the trigger control channel receives a first memory management command. For example, the trigger control channel may obtain the memory management command via the indicated interface from the configuration information. At block 406, the first memory management command is stored. At block 408, the trigger control channel detects a first one or more triggering events. For example, the trigger control channel may, based on the configuration information, monitor global and local events to detect one or more particular events. When the one or more particular events are detected, the trigger control channel is triggered.

At block 410 the trigger control channel triggers the stored first memory management command based on the detected first one or more triggering events. For example, the trigger control channel transmits the first memory management command to one or more queues for arbitration against other memory management commands. After winning in arbitration, the first memory management command may then be outputted for transmission to the appropriate memory location.

In this description, the term “couple” or “couples” means either an indirect or direct wired or wireless connection. Thus, if a first device couples to a second device, that connection may be through a direct connection or through an indirect connection via other devices and connections. The recitation “based on” means “based at least in part on.” Therefore, if X is based on Y, X may be a function of Y and any number of other factors.

Modifications are possible in the described embodiments, and other embodiments are possible, within the scope of the claims. While the specific embodiments described above have been shown by way of example, it will be appreciated that many modifications and other embodiments will come to the mind of one skilled in the art having the benefit of the teachings presented in the foregoing description and the associated drawings. Accordingly, it is understood that various modifications and embodiments are intended to be included within the scope of the appended claims. 

What is claimed is:
 1. A processing system comprising: one or more processors; a cache memory coupled to the one or more processors; and a memory controller comprising: one or more trigger control channels configured to: receive configuration information for a trigger control channel of the one or more trigger control channels, the configuration information defining a first one or more triggering events; receive a first memory management command; store the first memory management command; detect the first one or more triggering events; and trigger the stored first memory management command based on the detected first one or more triggering events.
 2. The processing system of claim 1, wherein the first one or more triggering events comprise at least one of receiving an event on a shared messaging interface or a set register bit value command received on a local bus.
 3. The processing system of claim 1, wherein the first one or more triggering event comprises an event received on a shared messaging interface.
 4. The processing system of claim 1, wherein the received configuration information comprises an indication of an interface to use to obtain the first memory management command.
 5. The processing system of claim 1, wherein the configuration information is obtained from a peripheral.
 6. The processing system of claim 1, wherein the memory controller further comprises return messaging circuitry configured to: receive a response to a memory access command; format the response based on a memory access command type; and output a formatted memory access command.
 7. The processing system of claim 6, wherein formatting the response comprises formatting a local event based on the response, and wherein the one or more trigger control channels are configured to trigger a second memory management command based on the local event.
 8. The processing system of claim 1, wherein the detected first one or more triggering events comprise at least one of a receiving an event on a shared messaging interface or a set register bit value command received on a local bus.
 9. The processing system of claim 1, wherein the one or more trigger control channels include two or more trigger control channels configured to: detect a second one or more triggering events; trigger a second memory management command based on the detected second one or more triggering events; and wherein the memory controller is configured to arbitrate between the first and second memory management command.
 10. A memory controller device coupled to one or more processors, the memory controller device comprising: one or more trigger control channels configured to: receive configuration information for a trigger control channel of the one or more trigger control channels, the configuration information defining a first one or more triggering events; receive a first memory management command; store the first memory management command; detect the first one or more triggering events; and trigger the stored first memory management command based on the detected first one or more triggering events.
 11. The memory controller device of claim 10, wherein the first one or more triggering events comprise at least one of receiving an event on a shared messaging interface or a set register bit value command received on a local bus.
 12. The memory controller device of claim 10, wherein the first one or more triggering event comprises an event received on a shared messaging interface.
 13. The memory controller device of claim 10, wherein the received configuration information comprises an indication of an interface to use to obtain the first memory management command.
 14. The memory controller device of claim 10, wherein the configuration information is obtained from a peripheral.
 15. The memory controller device of claim 10, wherein the memory controller further comprises return messaging circuitry configured to: receive a response to a memory access command; format the response based on a memory access command type; and output a formatted memory access command.
 16. The memory controller device of claim 15, wherein formatting the response comprises formatting a local event based on the response, and wherein the one or more trigger control channels are configured to trigger a second memory management command based on the local event.
 17. The memory controller device of claim 10, wherein the detected first one or more triggering events comprise at least one of a receiving an event on a shared messaging interface or a set register bit value command received on a local bus.
 18. The memory controller device of claim 10, wherein the one or more trigger control channels include two or more trigger control channels configured to: detect a second one or more triggering events; trigger a second memory management command based on the detected second one or more triggering events; and wherein the memory controller is configured to arbitrate between the first and second memory management command.
 19. A method for accessing memory by a memory controller, comprising: receiving configuration information for a trigger control channel of one or more trigger control channels, the configuration information defining a first one or more triggering events; receiving a first memory management command; storing the first memory management command; detecting the first one or more triggering events; and triggering the stored first memory management command based on the detected first one or more triggering events.
 20. The method of claim 19, further comprising: receiving a response to a memory access command; formatting the response based on a memory access command type; and outputting a formatted memory access command. 